Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create license.md #82

Merged
merged 2 commits into from
Nov 11, 2024
Merged

Create license.md #82

merged 2 commits into from
Nov 11, 2024

Conversation

gkorland
Copy link
Contributor

@gkorland gkorland commented Oct 31, 2024

Fix #81

Summary by CodeRabbit

  • New Features

    • Added new entries to the wordlist, including GPL, SDKs, codebase, and falkorDB.
    • Introduced a new licensing document, license.md, outlining terms for using FalkorDB under the Server Side Public License v1 (SSPLv1).
  • Documentation

    • The license.md file provides detailed information on licensing implications, modification rights, and usage conditions for FalkorDB.

Copy link
Contributor

coderabbitai bot commented Oct 31, 2024

Walkthrough

The changes include the addition of new entries to an existing wordlist file and the introduction of a new licensing document for FalkorDB. The wordlist now includes terms such as GPL, SDKs, codebase, and falkorDB, expanding the vocabulary related to programming and technology. The new license.md file outlines the licensing terms under the Server Side Public License v1 (SSPLv1), detailing user rights and obligations regarding the use and distribution of FalkorDB.

Changes

File Change Summary
.wordlist.txt Added new entries: GPL, SDKs, codebase, falkorDB.
license.md New file added detailing FalkorDB's licensing under SSPLv1, including user rights and obligations.

Poem

In the garden of code, new words take flight,
GPL and SDKs, shining so bright.
With falkorDB here, our tools now expand,
A license to guide us, a helping hand.
Let's hop through the changes, with joy and delight! 🐇✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@gkorland gkorland marked this pull request as ready for review November 11, 2024 15:22
@gkorland gkorland merged commit 0fd66b7 into main Nov 11, 2024
1 of 2 checks passed
@gkorland gkorland deleted the gkorland-patch-2 branch November 11, 2024 15:26
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Outside diff range and nitpick comments (3)
.wordlist.txt (1)

Line range hint 1-400: Remove duplicate entry and fix alphabetical ordering

The wordlist contains the following issues:

  1. Duplicate entries for "falkorDB" (one capitalized, one lowercase)
  2. Some terms appear to be out of alphabetical order
  3. Multiple trailing blank lines at the end of file

Apply these changes:

  1. Keep only one entry for "FalkorDB" (preferably the capitalized version since it's a product name)
  2. Ensure all entries are in alphabetical order
  3. Remove extra blank lines at the end of file, keeping just one

Here's a script to help identify out-of-order entries:

#!/bin/bash
# Description: Check for alphabetical ordering issues in the wordlist

# Create a sorted version and compare with original
sort .wordlist.txt | diff - .wordlist.txt

# Find duplicate entries (case-insensitive)
sort -f .wordlist.txt | uniq -i -d
🧰 Tools
🪛 LanguageTool

[uncategorized] ~29-~29: Ger doublet «GraphBLAS GraphBlas».
Context: ...BQAChain Gadepally Geospatial GPL GrAPL GraphBLAS GraphBlas GraphRAG IDF IDentifier IPDPS ISC Imple...

(GER_DOUBLET)

license.md (2)

9-9: Fix typos and standardize license name formatting

There are a few minor issues to address:

  1. Remove the duplicate "the" in the sentence
  2. Use consistent hyphenation for "Server-Side Public License" as it's a compound adjective
-FalkorDB is licensed under the the [Server Side Public License v1 (SSPLv1)]
+FalkorDB is licensed under the [Server-Side Public License v1 (SSPLv1)]
🧰 Tools
🪛 LanguageTool

[duplication] ~9-~9: Possible typo: you repeated a word
Context: ...rDB License FalkorDB is licensed under the the [Server Side Public License v1 (SSPLv1)...

(ENGLISH_WORD_REPEAT_RULE)


[uncategorized] ~9-~9: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...se FalkorDB is licensed under the the [Server Side Public License v1 (SSPLv1)](https://git...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


15-15: Standardize terminology throughout the document

For consistency and professionalism:

  1. Standardize "Server-Side Public License" with hyphens throughout
  2. Use consistent hyphenation for "open-source" when used as an adjective

Example changes needed:

-Server Side Public License
+Server-Side Public License
-open source your code
+open-source your code

Also applies to: 23-23, 27-27, 31-31, 35-35, 39-39, 43-43

🧰 Tools
🪛 LanguageTool

[uncategorized] ~15-~15: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...FalkorDB is licensed under SSPLv1? The Server Side Public License (SSPLv1) is designed to ...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between b141e48 and 12a668a.

📒 Files selected for processing (2)
  • .wordlist.txt (3 hunks)
  • license.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
license.md

[duplication] ~9-~9: Possible typo: you repeated a word
Context: ...rDB License FalkorDB is licensed under the the [Server Side Public License v1 (SSPLv1)...

(ENGLISH_WORD_REPEAT_RULE)


[uncategorized] ~9-~9: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...se FalkorDB is licensed under the the [Server Side Public License v1 (SSPLv1)](https://git...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[style] ~11-~11: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: .../FalkorDB/blob/master/LICENSE.txt). ## FalkorDB Licensing FAQ: Understanding the SSPLv1...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[uncategorized] ~15-~15: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...FalkorDB is licensed under SSPLv1? The Server Side Public License (SSPLv1) is designed to ...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

🔇 Additional comments (2)
.wordlist.txt (1)

28-28: LGTM: New entries are appropriate

The addition of technical terms GPL, SDKs, and codebase is appropriate for the project's documentation and aligns with the introduction of the license file.

Also applies to: 81-81, 110-110

license.md (1)

9-9: Verify license reference and consider using a stable branch

The license URL points to the master branch, which could change. Consider:

  1. Linking to a specific commit or release tag
  2. Verifying that the referenced license text matches the official SSPLv1
🧰 Tools
🪛 LanguageTool

[duplication] ~9-~9: Possible typo: you repeated a word
Context: ...rDB License FalkorDB is licensed under the the [Server Side Public License v1 (SSPLv1)...

(ENGLISH_WORD_REPEAT_RULE)


[uncategorized] ~9-~9: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...se FalkorDB is licensed under the the [Server Side Public License v1 (SSPLv1)](https://git...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

Comment on lines +23 to +24
If your closed-source project does not make FalkorDB available to external users as part of a service, you can use it without open-sourcing the rest of your code. However, if you provide FalkorDB as part of a service, the SSPLv1 requires you to open-source your codebase associated with the service.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Clarify the scope of "service" and code release requirements

The current wording about what constitutes a "service" and which parts of the code need to be open-sourced could be clearer. Consider adding specific examples or scenarios to help users better understand their obligations.

Suggested addition after line 32:

+For example:
+- If you run FalkorDB as an internal database, you don't need to open-source your application
+- If you offer FalkorDB as a managed database service, you must open-source the service implementation
+- If you embed FalkorDB in a self-hosted product, you don't need to open-source the product

Also applies to: 27-28, 31-32

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add a License FAQ
1 participant